Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c565d16d957f834f99a393993ad47aa79b386d61d67f1fe0f5c177f33e166f44

Tx prefix hash: f290c05bf56b47e4272c98d62ecab9226e4130e8f52a57b30a79f2098c788f7f
Tx public key: 9c064bd64c075e8370ff6c3118da056a43fa50255ee34c1ddb86e5a894ad049d
Timestamp: 1715677643 Timestamp [UCT]: 2024-05-14 09:07:23 Age [y:d:h:m:s]: 00:331:11:30:29
Block: 1021726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236928 RingCT/type: yes/0
Extra: 019c064bd64c075e8370ff6c3118da056a43fa50255ee34c1ddb86e5a894ad049d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e15ea502fadc17f78fd3d6fed5eab6df046d0573696bc6b0173f0151b38d469 0.600000000000 1486127 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": 1021736, "vin": [ { "gen": { "height": 1021726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e15ea502fadc17f78fd3d6fed5eab6df046d0573696bc6b0173f0151b38d469" } } ], "extra": [ 1, 156, 6, 75, 214, 76, 7, 94, 131, 112, 255, 108, 49, 24, 218, 5, 106, 67, 250, 80, 37, 94, 227, 76, 29, 219, 134, 229, 168, 148, 173, 4, 157, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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