Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 550d6d2921c90c0a324d9894ad0070630bd61072614e7d0f253d3f42b03d82a9

Tx prefix hash: e03b7a51963586788b1484fc842b9508aac81b72a889ddb7239a1a96a4f0406a
Tx public key: dd8e029df285fa24ca5671c9a8bcbf3a6665c022db8143f6bb5e8f5d32a6765e
Timestamp: 1718712105 Timestamp [UCT]: 2024-06-18 12:01:45 Age [y:d:h:m:s]: 01:145:13:13:08
Block: 1046881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362576 RingCT/type: yes/0
Extra: 01dd8e029df285fa24ca5671c9a8bcbf3a6665c022db8143f6bb5e8f5d32a6765e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50ae383a5ed76357f4189bce26c2c83586269c4a9510abc1835e5885ca8d463c 0.600000000000 1516700 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": 1046891, "vin": [ { "gen": { "height": 1046881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50ae383a5ed76357f4189bce26c2c83586269c4a9510abc1835e5885ca8d463c" } } ], "extra": [ 1, 221, 142, 2, 157, 242, 133, 250, 36, 202, 86, 113, 201, 168, 188, 191, 58, 102, 101, 192, 34, 219, 129, 67, 246, 187, 94, 143, 93, 50, 166, 118, 94, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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