Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d8720707076d9fa4bdf86636350acec3f6a6d7aef35bd60189815877e076e1

Tx prefix hash: 533bb52c0314b7b7f86863bd1ca23833662a5acd7a5e369b02beb47e4a761b82
Tx public key: caaa2cbdaf5e00818e29d2ee4c21590c7f75b16a45cc360333c90b22e78c7ddd
Timestamp: 1731395178 Timestamp [UCT]: 2024-11-12 07:06:18 Age [y:d:h:m:s]: 00:132:07:49:15
Block: 1151930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94401 RingCT/type: yes/0
Extra: 01caaa2cbdaf5e00818e29d2ee4c21590c7f75b16a45cc360333c90b22e78c7ddd021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c45f06f76fe2122f9f0e7e44f2656c37b3472166ded207b21a6abc00dbb9faf4 0.600000000000 1637515 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": 1151940, "vin": [ { "gen": { "height": 1151930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c45f06f76fe2122f9f0e7e44f2656c37b3472166ded207b21a6abc00dbb9faf4" } } ], "extra": [ 1, 202, 170, 44, 189, 175, 94, 0, 129, 142, 41, 210, 238, 76, 33, 89, 12, 127, 117, 177, 106, 69, 204, 54, 3, 51, 201, 11, 34, 231, 140, 125, 221, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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