Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0f48d4f7259c26dbdefb8a9d161b65b336adb7d667c3e03e756c3f7a37b0ab8

Tx prefix hash: 34a7a84e52b0a041526fbc1a82d0e6c05748cea81b2e84c665f38b408bc5e8cd
Tx public key: 0b7d6ffaea9409dfc5a5fbe04638dd35ea47e823ca0c8d3c5b40fbebd3ce8c03
Timestamp: 1716197599 Timestamp [UCT]: 2024-05-20 09:33:19 Age [y:d:h:m:s]: 00:237:01:12:38
Block: 1026030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169662 RingCT/type: yes/0
Extra: 010b7d6ffaea9409dfc5a5fbe04638dd35ea47e823ca0c8d3c5b40fbebd3ce8c0302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a55c05e1dbe9e890652edd36ec20e663eddaee1c865a558156a9fbb738ab10a 0.600000000000 1492891 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": 1026040, "vin": [ { "gen": { "height": 1026030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a55c05e1dbe9e890652edd36ec20e663eddaee1c865a558156a9fbb738ab10a" } } ], "extra": [ 1, 11, 125, 111, 250, 234, 148, 9, 223, 197, 165, 251, 224, 70, 56, 221, 53, 234, 71, 232, 35, 202, 12, 141, 60, 91, 64, 251, 235, 211, 206, 140, 3, 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