Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13797cd15f3de54d6a9b8b29f1c08c1f8fcf9f0d3834f9bdcfe12cdb25f34344

Tx prefix hash: da311456027236009d40f03a629170aa0b38c179fc4d66ae7e725ebbd61cf8c7
Tx public key: b4c2d28b2b1347b198d4e5bba6a4da7747af949831156bfc42c27041d42df649
Timestamp: 1738240357 Timestamp [UCT]: 2025-01-30 12:32:37 Age [y:d:h:m:s]: 00:137:20:16:34
Block: 1208354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98493 RingCT/type: yes/0
Extra: 01b4c2d28b2b1347b198d4e5bba6a4da7747af949831156bfc42c27041d42df649021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4f365e161ce26f62872ac7a00af87d438ee0d7e3e01e1d304a63808de375da9 0.600000000000 1695085 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": 1208364, "vin": [ { "gen": { "height": 1208354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4f365e161ce26f62872ac7a00af87d438ee0d7e3e01e1d304a63808de375da9" } } ], "extra": [ 1, 180, 194, 210, 139, 43, 19, 71, 177, 152, 212, 229, 187, 166, 164, 218, 119, 71, 175, 148, 152, 49, 21, 107, 252, 66, 194, 112, 65, 212, 45, 246, 73, 2, 17, 0, 0, 0, 1, 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