Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222e1a52ed1cdcfe7bbd73b517d048c134c546b61f33d9aad3c9dd7644103cd8

Tx prefix hash: 1253f0788facc3fd8584a891992599d1a3d67d8500bd3ea3bcdfeef3abcde265
Tx public key: 81f755890dfa45dc27edc5d0876f1eb80940364b710851bce2c58599ccf3192e
Timestamp: 1705087242 Timestamp [UCT]: 2024-01-12 19:20:42 Age [y:d:h:m:s]: 01:134:01:04:08
Block: 933910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356944 RingCT/type: yes/0
Extra: 0181f755890dfa45dc27edc5d0876f1eb80940364b710851bce2c58599ccf3192e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a94496eee67f0be2ce1082b8b00e6a631c078cc1aa77c8cd25a2d2a5ab5bbbd 0.600000000000 1391894 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": 933920, "vin": [ { "gen": { "height": 933910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a94496eee67f0be2ce1082b8b00e6a631c078cc1aa77c8cd25a2d2a5ab5bbbd" } } ], "extra": [ 1, 129, 247, 85, 137, 13, 250, 69, 220, 39, 237, 197, 208, 135, 111, 30, 184, 9, 64, 54, 75, 113, 8, 81, 188, 226, 197, 133, 153, 204, 243, 25, 46, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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