Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029d598a53402446f1519c8beba81cef23036a96b574ecb7f4cdd280a742b3c3

Tx prefix hash: aa7e312a949e2c4d2c01c94241d69ac5f2fdf9e0924b3c3bf9451f6c5022c6de
Tx public key: acd1667911a7f30e16d7121cac18c2f5d717e8bf68e925a1cf813a9663e6a49f
Timestamp: 1638314701 Timestamp [UCT]: 2021-11-30 23:25:01 Age [y:d:h:m:s]: 03:083:10:52:16
Block: 385695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 838302 RingCT/type: yes/0
Extra: 01acd1667911a7f30e16d7121cac18c2f5d717e8bf68e925a1cf813a9663e6a49f02110000000337cb3088000000000000000000

1 output(s) for total of 32.361804337000 dcy

stealth address amount amount idx
00: ad25bcb017bebc4b5fc87734728abacb3d605278b1f3c4b527e8a8cb588f169e 32.361804337000 778292 of 0

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": 385705, "vin": [ { "gen": { "height": 385695 } } ], "vout": [ { "amount": 32361804337, "target": { "key": "ad25bcb017bebc4b5fc87734728abacb3d605278b1f3c4b527e8a8cb588f169e" } } ], "extra": [ 1, 172, 209, 102, 121, 17, 167, 243, 14, 22, 215, 18, 28, 172, 24, 194, 245, 215, 23, 232, 191, 104, 233, 37, 161, 207, 129, 58, 150, 99, 230, 164, 159, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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