Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8228b4c13fbad7dcca39b23143f92ad04e8b7994591a6cd8d18497937a37d2af

Tx prefix hash: 0f68e6de986e427908aae2c26db781792c6c829409e18fcb9861b95710928bf0
Tx public key: 079f5b00cf80d40dd4c5bee85b7d47f111954d248828f9be9b13a6892ad56da8
Timestamp: 1696917368 Timestamp [UCT]: 2023-10-10 05:56:08 Age [y:d:h:m:s]: 01:104:22:52:56
Block: 866395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336224 RingCT/type: yes/0
Extra: 01079f5b00cf80d40dd4c5bee85b7d47f111954d248828f9be9b13a6892ad56da802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.826558773000 dcy

stealth address amount amount idx
00: c1d22e05c0409abbcc26c31416f58dca943f3200fbb5dbc0eafcf9038ef44438 0.826558773000 1320985 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": 866405, "vin": [ { "gen": { "height": 866395 } } ], "vout": [ { "amount": 826558773, "target": { "key": "c1d22e05c0409abbcc26c31416f58dca943f3200fbb5dbc0eafcf9038ef44438" } } ], "extra": [ 1, 7, 159, 91, 0, 207, 128, 212, 13, 212, 197, 190, 232, 91, 125, 71, 241, 17, 149, 77, 36, 136, 40, 249, 190, 155, 19, 166, 137, 42, 213, 109, 168, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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