Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24cbd90e0fac946dabe9a8d9f1b7740dd8d71221f1065a83c2206ee977da0f6b

Tx prefix hash: 01cd36c69d531aee4b6a8160dcefaeb4e6f8a97f44f2d341aaa6ec966cfd5536
Tx public key: e7355172f89bdcee9c875882474b333cb3c4c8145ae3a591b58ed900d802becf
Timestamp: 1735866765 Timestamp [UCT]: 2025-01-03 01:12:45 Age [y:d:h:m:s]: 00:301:22:55:28
Block: 1188968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213307 RingCT/type: yes/0
Extra: 01e7355172f89bdcee9c875882474b333cb3c4c8145ae3a591b58ed900d802becf021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8305efb71a74c883e224020676b7cfca7e91549a10ef9d027287d6d084b3432 0.600000000000 1675473 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": 1188978, "vin": [ { "gen": { "height": 1188968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8305efb71a74c883e224020676b7cfca7e91549a10ef9d027287d6d084b3432" } } ], "extra": [ 1, 231, 53, 81, 114, 248, 155, 220, 238, 156, 135, 88, 130, 71, 75, 51, 60, 179, 196, 200, 20, 90, 227, 165, 145, 181, 142, 217, 0, 216, 2, 190, 207, 2, 17, 0, 0, 0, 7, 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