Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d96e2dc1413a4b4688c40d264922936dbabfbf5cee71b4a8dbe5d0cf939ec868

Tx prefix hash: c44e8e6b7217f20bd20067296af50e75be47c6aa13cc381796ad50f6529da9ea
Tx public key: 8fbdcd7dd239d28f8b3a8d1840228008c20c69905cc5239646283dc3947a2f8b
Timestamp: 1732716969 Timestamp [UCT]: 2024-11-27 14:16:09 Age [y:d:h:m:s]: 00:128:08:20:05
Block: 1162890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91531 RingCT/type: yes/0
Extra: 018fbdcd7dd239d28f8b3a8d1840228008c20c69905cc5239646283dc3947a2f8b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f51b98ddd44f47a3ac5049bbb2b95efe5df057f0110788a45ffe869a02369fc 0.600000000000 1648553 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": 1162900, "vin": [ { "gen": { "height": 1162890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f51b98ddd44f47a3ac5049bbb2b95efe5df057f0110788a45ffe869a02369fc" } } ], "extra": [ 1, 143, 189, 205, 125, 210, 57, 210, 143, 139, 58, 141, 24, 64, 34, 128, 8, 194, 12, 105, 144, 92, 197, 35, 150, 70, 40, 61, 195, 148, 122, 47, 139, 2, 17, 0, 0, 0, 1, 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