Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59f902dba4ac9fe13c0e1a18c1c89314b72ffcf197451b1870852a0155354592

Tx prefix hash: b0c9fd1909e83a96d8968829d0a6373c3a19e7ef27232869d118b3ef57229a1f
Tx public key: 2c1133775cb1c695e273874d7bf8147b58650f9af317a00b19d314a530dc32c6
Timestamp: 1744993804 Timestamp [UCT]: 2025-04-18 16:30:04 Age [y:d:h:m:s]: 00:026:01:07:55
Block: 1264261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18640 RingCT/type: yes/0
Extra: 012c1133775cb1c695e273874d7bf8147b58650f9af317a00b19d314a530dc32c60211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 646ec052f23f4d5c39588e9b1c599a0d57ed4a61272352911c22dc8105227fd5 0.600000000000 1751456 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": 1264271, "vin": [ { "gen": { "height": 1264261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "646ec052f23f4d5c39588e9b1c599a0d57ed4a61272352911c22dc8105227fd5" } } ], "extra": [ 1, 44, 17, 51, 119, 92, 177, 198, 149, 226, 115, 135, 77, 123, 248, 20, 123, 88, 101, 15, 154, 243, 23, 160, 11, 25, 211, 20, 165, 48, 220, 50, 198, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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