Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73ad2cf97dbe09ea5c76322ba734539e8df8d9b8b16824875772752c33276880

Tx prefix hash: c54789982effdbddd36ea166659cd7025f50e928bb5078f1669021e5aa1c5794
Tx public key: cd7b2d6603599ce9f663d844e5f4a066f6f316177fde8e8e79a8ed985a54c25e
Timestamp: 1703761484 Timestamp [UCT]: 2023-12-28 11:04:44 Age [y:d:h:m:s]: 01:144:23:05:00
Block: 922926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364756 RingCT/type: yes/0
Extra: 01cd7b2d6603599ce9f663d844e5f4a066f6f316177fde8e8e79a8ed985a54c25e0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 440a0d8f86be1f0939eccb027a6984cf18dcd0d2853d7ace7d7a5a2e51303834 0.600000000000 1380632 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": 922936, "vin": [ { "gen": { "height": 922926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "440a0d8f86be1f0939eccb027a6984cf18dcd0d2853d7ace7d7a5a2e51303834" } } ], "extra": [ 1, 205, 123, 45, 102, 3, 89, 156, 233, 246, 99, 216, 68, 229, 244, 160, 102, 246, 243, 22, 23, 127, 222, 142, 142, 121, 168, 237, 152, 90, 84, 194, 94, 2, 17, 0, 0, 0, 6, 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