Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aba97e4ef7a5344890c870c7da2097aef73c104647f148fdbf37ba313588dc9f

Tx prefix hash: 9be38c9890daa0b4049aa1e387148c3c3521be2a9c9e4e01e31f5c8c42cf8bb0
Tx public key: d27be7806d4b567dc70ef889106af4d26882f54cd905a595bbf78b4e84d2335c
Timestamp: 1731387432 Timestamp [UCT]: 2024-11-12 04:57:12 Age [y:d:h:m:s]: 00:142:09:21:36
Block: 1151868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101591 RingCT/type: yes/0
Extra: 01d27be7806d4b567dc70ef889106af4d26882f54cd905a595bbf78b4e84d2335c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d34887e5044e7a7967cfd2c1d737c5196d272bb212d6aaa3c8ee39d2e173c36 0.600000000000 1637451 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": 1151878, "vin": [ { "gen": { "height": 1151868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d34887e5044e7a7967cfd2c1d737c5196d272bb212d6aaa3c8ee39d2e173c36" } } ], "extra": [ 1, 210, 123, 231, 128, 109, 75, 86, 125, 199, 14, 248, 137, 16, 106, 244, 210, 104, 130, 245, 76, 217, 5, 165, 149, 187, 247, 139, 78, 132, 210, 51, 92, 2, 17, 0, 0, 0, 3, 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