Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea3d0c9e7e71989192ca94c0de7ca7a8efda4515994b7ea777bb09bbc7753186

Tx prefix hash: d85dbe4a58c1b6558a50edf3799a9b55ced34f9ceb7676526bdd06aed6fee4ab
Tx public key: 0bc8e35146348ed5ba08f57f5b9fddfb4adf1a06ff0196fbd590c0223ccda094
Timestamp: 1734633831 Timestamp [UCT]: 2024-12-19 18:43:51 Age [y:d:h:m:s]: 00:105:06:56:55
Block: 1178790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75003 RingCT/type: yes/0
Extra: 010bc8e35146348ed5ba08f57f5b9fddfb4adf1a06ff0196fbd590c0223ccda094021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 327f76406c20f44d958476514340bdc9c8d1e6e2caea4dd0ea66405d8e343b0a 0.600000000000 1665179 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": 1178800, "vin": [ { "gen": { "height": 1178790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "327f76406c20f44d958476514340bdc9c8d1e6e2caea4dd0ea66405d8e343b0a" } } ], "extra": [ 1, 11, 200, 227, 81, 70, 52, 142, 213, 186, 8, 245, 127, 91, 159, 221, 251, 74, 223, 26, 6, 255, 1, 150, 251, 213, 144, 192, 34, 60, 205, 160, 148, 2, 17, 0, 0, 0, 3, 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