Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c0532bd62b5e61fe554470a9d89810b01b20a5208965f054721eea5d8e2779

Tx prefix hash: 0df4a9a13d5274627a6bf21b352d83b71402ca4b5ac3a421b8bc60bc02991a1e
Tx public key: 97e9517090f08e42570da9e4dedd8d2ca45b7a754db85a28c112bb447218eea3
Timestamp: 1711626481 Timestamp [UCT]: 2024-03-28 11:48:01 Age [y:d:h:m:s]: 01:252:11:09:43
Block: 988145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439138 RingCT/type: yes/0
Extra: 0197e9517090f08e42570da9e4dedd8d2ca45b7a754db85a28c112bb447218eea30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b521540c1d110265bf794505db9f924c3afee2aa24435cacf3f4e9c8034f96 0.600000000000 1448412 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": 988155, "vin": [ { "gen": { "height": 988145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b521540c1d110265bf794505db9f924c3afee2aa24435cacf3f4e9c8034f96" } } ], "extra": [ 1, 151, 233, 81, 112, 144, 240, 142, 66, 87, 13, 169, 228, 222, 221, 141, 44, 164, 91, 122, 117, 77, 184, 90, 40, 193, 18, 187, 68, 114, 24, 238, 163, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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