Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e55cb7cde2c3bcf0426c76c1a67613c0d2106eec52b71c2b47c34f0f2a52471d

Tx prefix hash: e609bd5b0b0af1f9cab8d1029f74a7af416c170db14f221a8ce5c4b99ad8d6d0
Tx public key: 141c705de46743a5cfd6af79982f68dd08561a6571a10007df7802c8aa26ac83
Timestamp: 1721817713 Timestamp [UCT]: 2024-07-24 10:41:53 Age [y:d:h:m:s]: 00:123:01:27:45
Block: 1072616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88052 RingCT/type: yes/0
Extra: 01141c705de46743a5cfd6af79982f68dd08561a6571a10007df7802c8aa26ac8302110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cde1ae383fa5d508c2f097f9e8b02076495333ab357ec3f23f6882e79ef0d0cf 0.600000000000 1545101 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": 1072626, "vin": [ { "gen": { "height": 1072616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cde1ae383fa5d508c2f097f9e8b02076495333ab357ec3f23f6882e79ef0d0cf" } } ], "extra": [ 1, 20, 28, 112, 93, 228, 103, 67, 165, 207, 214, 175, 121, 152, 47, 104, 221, 8, 86, 26, 101, 113, 161, 0, 7, 223, 120, 2, 200, 170, 38, 172, 131, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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