Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adf0da52bd1c2e521b9e8ca7942a49d8bd94ff4a2bb00b4d6189a147e34376c1

Tx prefix hash: 3615e17978ee9a57446366744a6b9840991c6e77df4ac0cafb5b1e117e2d6e87
Tx public key: 1aaaa4d50d2ae2220518d090ad1dd34cef1417f3b52e4d9844a90982fcbaab62
Timestamp: 1702017906 Timestamp [UCT]: 2023-12-08 06:45:06 Age [y:d:h:m:s]: 01:081:17:39:17
Block: 908479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319520 RingCT/type: yes/0
Extra: 011aaaa4d50d2ae2220518d090ad1dd34cef1417f3b52e4d9844a90982fcbaab62021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 253555b7eace7720d9f441482db985389a88b2fc323c6200755c21e381ceb88a 0.600000000000 1365512 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": 908489, "vin": [ { "gen": { "height": 908479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "253555b7eace7720d9f441482db985389a88b2fc323c6200755c21e381ceb88a" } } ], "extra": [ 1, 26, 170, 164, 213, 13, 42, 226, 34, 5, 24, 208, 144, 173, 29, 211, 76, 239, 20, 23, 243, 181, 46, 77, 152, 68, 169, 9, 130, 252, 186, 171, 98, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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