Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b1ae63c1bd8706694fc312d9caaf8aeae991c22134341b4b543e912e612229

Tx prefix hash: 2e57759d2e0b63ef2b36ff7db2d2207324506c2c77867bb38d822ead7e72d6da
Tx public key: 36e88855a40a1372dacd1f5f2c99be6508fadfb3a3c574e04fd049776cb39aa8
Timestamp: 1672283672 Timestamp [UCT]: 2022-12-29 03:14:32 Age [y:d:h:m:s]: 01:341:22:59:06
Block: 662823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505431 RingCT/type: yes/0
Extra: 0136e88855a40a1372dacd1f5f2c99be6508fadfb3a3c574e04fd049776cb39aa8021100000001e7ace25d000000000000000000

1 output(s) for total of 3.906539481000 dcy

stealth address amount amount idx
00: cce837c8601d0d0edbf00f79860a21ce2a0bae54a6f910b87808c79a14acd63f 3.906539481000 1103692 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": 662833, "vin": [ { "gen": { "height": 662823 } } ], "vout": [ { "amount": 3906539481, "target": { "key": "cce837c8601d0d0edbf00f79860a21ce2a0bae54a6f910b87808c79a14acd63f" } } ], "extra": [ 1, 54, 232, 136, 85, 164, 10, 19, 114, 218, 205, 31, 95, 44, 153, 190, 101, 8, 250, 223, 179, 163, 197, 116, 224, 79, 208, 73, 119, 108, 179, 154, 168, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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