Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8236d5f44af653b52f57916b371ad6a16d2ae7f231e695d500039217bf85a9e3

Tx prefix hash: da625c575e1bc4f32b5f842c38db33cf5ca784ed854705702d083a9be711afd5
Tx public key: 6869102f169b44e31333b2d04c31f62bf27cb7e349c23f4e44cbde61b41a7cb1
Timestamp: 1726682670 Timestamp [UCT]: 2024-09-18 18:04:30 Age [y:d:h:m:s]: 00:224:04:53:32
Block: 1112955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160075 RingCT/type: yes/0
Extra: 016869102f169b44e31333b2d04c31f62bf27cb7e349c23f4e44cbde61b41a7cb102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c6c84e45f87ef2982bf4d4955caf9dc29d3f7613728fa0489a76e57f691eb6f 0.600000000000 1592458 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": 1112965, "vin": [ { "gen": { "height": 1112955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c6c84e45f87ef2982bf4d4955caf9dc29d3f7613728fa0489a76e57f691eb6f" } } ], "extra": [ 1, 104, 105, 16, 47, 22, 155, 68, 227, 19, 51, 178, 208, 76, 49, 246, 43, 242, 124, 183, 227, 73, 194, 63, 78, 68, 203, 222, 97, 180, 26, 124, 177, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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