Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ae990636cf7366c5364b1c8b25f05cb9cb471888bc2c52fdc6d08d5a10eedf

Tx prefix hash: 297280d458896e24b8cc145020521b007007a38c6ff4a178f4ff8b788d316eb3
Tx public key: 4248c68d284791c4c4a695196ff2030d785350fb8b1fa234526ac2eb7b4297dd
Timestamp: 1736272056 Timestamp [UCT]: 2025-01-07 17:47:36 Age [y:d:h:m:s]: 00:086:06:07:45
Block: 1192323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61431 RingCT/type: yes/0
Extra: 014248c68d284791c4c4a695196ff2030d785350fb8b1fa234526ac2eb7b4297dd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a0bd8dc402d96031531df00f8d62a2a598efcde9d15fd106f6f9d88e6240ae3 0.600000000000 1678872 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": 1192333, "vin": [ { "gen": { "height": 1192323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a0bd8dc402d96031531df00f8d62a2a598efcde9d15fd106f6f9d88e6240ae3" } } ], "extra": [ 1, 66, 72, 198, 141, 40, 71, 145, 196, 196, 166, 149, 25, 111, 242, 3, 13, 120, 83, 80, 251, 139, 31, 162, 52, 82, 106, 194, 235, 123, 66, 151, 221, 2, 17, 0, 0, 0, 1, 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