Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14786d6bb63ebcdce23bbd4b4cc48cc238d5dbdc2d4a8af8f88093ecf3e7efd

Tx prefix hash: 17861e623a156cad3ce2495a2d06c6bd4850517f7222c04891f4d99bd2a76c62
Tx public key: 6836f217d6814a25f1ff3065e96fe00f986527974df35635da8f36f2df4858f2
Timestamp: 1763618339 Timestamp [UCT]: 2025-11-20 05:58:59 Age [y:d:h:m:s]: 00:052:00:26:05
Block: 1416045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37251 RingCT/type: yes/0
Extra: 016836f217d6814a25f1ff3065e96fe00f986527974df35635da8f36f2df4858f202110000000334af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eaf23dcb345dc7e79e2a6d466e1f99fbd3ba842c421c297c74288e31d3fd4e0 0.600000000000 1904564 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": 1416055, "vin": [ { "gen": { "height": 1416045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eaf23dcb345dc7e79e2a6d466e1f99fbd3ba842c421c297c74288e31d3fd4e0" } } ], "extra": [ 1, 104, 54, 242, 23, 214, 129, 74, 37, 241, 255, 48, 101, 233, 111, 224, 15, 152, 101, 39, 151, 77, 243, 86, 53, 218, 143, 54, 242, 223, 72, 88, 242, 2, 17, 0, 0, 0, 3, 52, 175, 49, 204, 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