Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec877d44c3eceed92faf1c2deba2fb789695b975be8e862d70349efccab4e747

Tx prefix hash: ed4a263dd24c7f8771227e839ee5b5de89b09997c735cd30fd612cf86be76226
Tx public key: 52a7d261b84e7fa1f8fd65666a73ec56ff600b6c5842142fedd78aa08c4533fa
Timestamp: 1737513034 Timestamp [UCT]: 2025-01-22 02:30:34 Age [y:d:h:m:s]: 00:150:04:29:44
Block: 1202554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107045 RingCT/type: yes/0
Extra: 0152a7d261b84e7fa1f8fd65666a73ec56ff600b6c5842142fedd78aa08c4533fa02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 327a17bceb3f3c2a043e5c4627d73f9285eaea5845fe1e1acc17b72e0e250a5b 0.600000000000 1689219 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": 1202564, "vin": [ { "gen": { "height": 1202554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "327a17bceb3f3c2a043e5c4627d73f9285eaea5845fe1e1acc17b72e0e250a5b" } } ], "extra": [ 1, 82, 167, 210, 97, 184, 78, 127, 161, 248, 253, 101, 102, 106, 115, 236, 86, 255, 96, 11, 108, 88, 66, 20, 47, 237, 215, 138, 160, 140, 69, 51, 250, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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