Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b24ed21760fbca1b99f19a451e6396c66ef4be31eb08c164a2c0d8b83cca0b

Tx prefix hash: ead2bee0836c68b30dcdceb8166d36f6815e827a25a681dd73abee2b89581e48
Tx public key: d4049f89d5d7ef3867719224bcf651bff01f5f58f0794c8da59d6f70e6876a29
Timestamp: 1726065602 Timestamp [UCT]: 2024-09-11 14:40:02 Age [y:d:h:m:s]: 00:119:14:22:34
Block: 1107840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85530 RingCT/type: yes/0
Extra: 01d4049f89d5d7ef3867719224bcf651bff01f5f58f0794c8da59d6f70e6876a29021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d25d8dacdc3a96d443965a0c56dcec6af6cd8c088295e9eb158c347fb7f46bd8 0.600000000000 1585527 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": 1107850, "vin": [ { "gen": { "height": 1107840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d25d8dacdc3a96d443965a0c56dcec6af6cd8c088295e9eb158c347fb7f46bd8" } } ], "extra": [ 1, 212, 4, 159, 137, 213, 215, 239, 56, 103, 113, 146, 36, 188, 246, 81, 191, 240, 31, 95, 88, 240, 121, 76, 141, 165, 157, 111, 112, 230, 135, 106, 41, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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