Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248e868ef7a0e414b8c1d43d288cee49bb4edc237991060efa0a8301baee0799

Tx prefix hash: 5c5e800ef2d21a290f103f8659f13b6345e8847e5089c6d57c51f3359af58274
Tx public key: 4a89c8d6d29661feda81aa86d5a5f9a6edef34947e67bf6019a6bb91590d4f99
Timestamp: 1717827720 Timestamp [UCT]: 2024-06-08 06:22:00 Age [y:d:h:m:s]: 00:228:05:17:59
Block: 1039546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163277 RingCT/type: yes/0
Extra: 014a89c8d6d29661feda81aa86d5a5f9a6edef34947e67bf6019a6bb91590d4f99021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 717573cf791b3ad5afeb9c28c6ddde2ae462b382e53adca41e4e70bbbe1a2755 0.600000000000 1508189 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": 1039556, "vin": [ { "gen": { "height": 1039546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "717573cf791b3ad5afeb9c28c6ddde2ae462b382e53adca41e4e70bbbe1a2755" } } ], "extra": [ 1, 74, 137, 200, 214, 210, 150, 97, 254, 218, 129, 170, 134, 213, 165, 249, 166, 237, 239, 52, 148, 126, 103, 191, 96, 25, 166, 187, 145, 89, 13, 79, 153, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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