Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f394f74699780a2db73ee6e7c5384fcb5bd5279f41ffa3bb5a213cdff1c0d4f0

Tx prefix hash: 966c71e4da74eb4c473d2eac89e92dd13c48b599f51d7ccb044722aadf0e91b4
Tx public key: f088cad0280e7c04be4a015feb884f0a1cd98089fb093df9b62d1d7ae191f1a8
Timestamp: 1733193524 Timestamp [UCT]: 2024-12-03 02:38:44 Age [y:d:h:m:s]: 00:352:10:41:42
Block: 1166841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249413 RingCT/type: yes/0
Extra: 01f088cad0280e7c04be4a015feb884f0a1cd98089fb093df9b62d1d7ae191f1a8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c2dfa134db78e98be7a22ebc054e3a84698eb525ff3f7d50becd9067f22dff9 0.600000000000 1652532 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1166851, "vin": [ { "gen": { "height": 1166841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c2dfa134db78e98be7a22ebc054e3a84698eb525ff3f7d50becd9067f22dff9" } } ], "extra": [ 1, 240, 136, 202, 208, 40, 14, 124, 4, 190, 74, 1, 95, 235, 136, 79, 10, 28, 217, 128, 137, 251, 9, 61, 249, 182, 45, 29, 122, 225, 145, 241, 168, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8