Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43c2e9f7bd72ee861fbc97f4b405a8922faaea9408a92ea23ecd0e055471551

Tx prefix hash: badfebf4ab6d9b57a3fb63791a76d57ca5016de2aca5f8418e060f5af74d03c3
Tx public key: cf1184f751eb40cc0f52e64cbe34a3e784ae5365300567bb746072112333b62a
Timestamp: 1717897868 Timestamp [UCT]: 2024-06-09 01:51:08 Age [y:d:h:m:s]: 01:006:20:02:11
Block: 1040132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265675 RingCT/type: yes/0
Extra: 01cf1184f751eb40cc0f52e64cbe34a3e784ae5365300567bb746072112333b62a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea0d4bafb33e90d5a5a0fd28a0135a64c38dc2a23e5b8368e82bdd82d80f093 0.600000000000 1508787 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": 1040142, "vin": [ { "gen": { "height": 1040132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea0d4bafb33e90d5a5a0fd28a0135a64c38dc2a23e5b8368e82bdd82d80f093" } } ], "extra": [ 1, 207, 17, 132, 247, 81, 235, 64, 204, 15, 82, 230, 76, 190, 52, 163, 231, 132, 174, 83, 101, 48, 5, 103, 187, 116, 96, 114, 17, 35, 51, 182, 42, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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