Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23786d6208b944215f18df9e83eddd66132d811bb458f014c50cc33232e61d69

Tx prefix hash: d9ae1a8ad64411338f7d0e324fda320d9244e53d3a9831e7cf75ce0820b22c4d
Tx public key: 2f56b0e2d4f4d980faf6eaa841b8dfc766db375156804097b20c9e1ad4249979
Timestamp: 1724549660 Timestamp [UCT]: 2024-08-25 01:34:20 Age [y:d:h:m:s]: 00:277:02:02:31
Block: 1095300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197916 RingCT/type: yes/0
Extra: 012f56b0e2d4f4d980faf6eaa841b8dfc766db375156804097b20c9e1ad4249979021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5ced369a73714872060222fb1a978e41a0f96146dc3261e616a5c83f16b2241 0.600000000000 1570461 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": 1095310, "vin": [ { "gen": { "height": 1095300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5ced369a73714872060222fb1a978e41a0f96146dc3261e616a5c83f16b2241" } } ], "extra": [ 1, 47, 86, 176, 226, 212, 244, 217, 128, 250, 246, 234, 168, 65, 184, 223, 199, 102, 219, 55, 81, 86, 128, 64, 151, 178, 12, 158, 26, 212, 36, 153, 121, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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