Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a6adae21c839c1a47f7a0f1b95f1043240f68565604fe3bbd89791ac6dc3142

Tx prefix hash: 0c8c3a70e10edade687c959885fd1d29a0acedc982c1ef895e6f756d83ec7cb5
Tx public key: c1293d8496aa4e9da0d23e96ff06d2584943f9cb88acf0e00da3ae42cf4587d6
Timestamp: 1733940667 Timestamp [UCT]: 2024-12-11 18:11:07 Age [y:d:h:m:s]: 00:324:04:08:34
Block: 1173043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229174 RingCT/type: yes/0
Extra: 01c1293d8496aa4e9da0d23e96ff06d2584943f9cb88acf0e00da3ae42cf4587d6021100000002c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8fb349ba9b86a778be18c66fbfaddbf114df062c060dc541a4f3ee6b0526ee4 0.600000000000 1659016 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": 1173053, "vin": [ { "gen": { "height": 1173043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8fb349ba9b86a778be18c66fbfaddbf114df062c060dc541a4f3ee6b0526ee4" } } ], "extra": [ 1, 193, 41, 61, 132, 150, 170, 78, 157, 160, 210, 62, 150, 255, 6, 210, 88, 73, 67, 249, 203, 136, 172, 240, 224, 13, 163, 174, 66, 207, 69, 135, 214, 2, 17, 0, 0, 0, 2, 199, 202, 20, 193, 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