Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f251aa0aab443f795ced6b7f70a2e2e31e307bb3e6acc40495aeac1a11c78af

Tx prefix hash: 16a669cd9ae808beb6f08e6d33464894a856ab67009f58d43c8dd99423065cf0
Tx public key: 9bfe7a77e0835a41d4c9e3591fc040fff88fcd9c7542716f12ef924a173cb7f4
Timestamp: 1759394463 Timestamp [UCT]: 2025-10-02 08:41:03 Age [y:d:h:m:s]: 00:094:02:05:51
Block: 1381037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67391 RingCT/type: yes/0
Extra: 019bfe7a77e0835a41d4c9e3591fc040fff88fcd9c7542716f12ef924a173cb7f402110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98b9d75a94b8e275df139de05bed0aa9c0dfa0413bdc61b947921268542f555 0.600000000000 1869148 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": 1381047, "vin": [ { "gen": { "height": 1381037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98b9d75a94b8e275df139de05bed0aa9c0dfa0413bdc61b947921268542f555" } } ], "extra": [ 1, 155, 254, 122, 119, 224, 131, 90, 65, 212, 201, 227, 89, 31, 192, 64, 255, 248, 143, 205, 156, 117, 66, 113, 111, 18, 239, 146, 74, 23, 60, 183, 244, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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