Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bd0a58870b1801c8912c8305f540b99b77e62ddcbe6c3efc11782d96e43d14e

Tx prefix hash: 62b0dfc05a0e8a6d98b9d0f9a597045f2f555855c8c7113904fa8a9da14ce05d
Tx public key: 0381e374156043bb0ad106d2ebf9c6a45dbc6a32e1450d66f229ac5c8ec7c784
Timestamp: 1731867636 Timestamp [UCT]: 2024-11-17 18:20:36 Age [y:d:h:m:s]: 00:209:12:30:25
Block: 1155852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149513 RingCT/type: yes/0
Extra: 010381e374156043bb0ad106d2ebf9c6a45dbc6a32e1450d66f229ac5c8ec7c784021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42b660c374479440e797f3c04f159f25790b43a4ff4895a5e606763db0a72c8a 0.600000000000 1641471 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": 1155862, "vin": [ { "gen": { "height": 1155852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42b660c374479440e797f3c04f159f25790b43a4ff4895a5e606763db0a72c8a" } } ], "extra": [ 1, 3, 129, 227, 116, 21, 96, 67, 187, 10, 209, 6, 210, 235, 249, 198, 164, 93, 188, 106, 50, 225, 69, 13, 102, 242, 41, 172, 92, 142, 199, 199, 132, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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