Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16df65d0e6b95aefd2960e1273ebe19aabec8def992a54e291a03f54105a3f4

Tx prefix hash: 147facb05fa1e3b47004f970ee65d1f4ea6c1deaf30a436fa2912611958f9c80
Tx public key: b7ee0fda36d33c8a89f9a401392bbd30b5a76bc348a50234431bc15ee639659d
Timestamp: 1761757996 Timestamp [UCT]: 2025-10-29 17:13:16 Age [y:d:h:m:s]: 00:020:00:37:13
Block: 1400641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14331 RingCT/type: yes/0
Extra: 01b7ee0fda36d33c8a89f9a401392bbd30b5a76bc348a50234431bc15ee639659d02110000000825a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa0ae8a27763b03e271e39a26b5d2f420328a5a7688559a7a5ddbf699be5b8f6 0.600000000000 1888958 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": 1400651, "vin": [ { "gen": { "height": 1400641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa0ae8a27763b03e271e39a26b5d2f420328a5a7688559a7a5ddbf699be5b8f6" } } ], "extra": [ 1, 183, 238, 15, 218, 54, 211, 60, 138, 137, 249, 164, 1, 57, 43, 189, 48, 181, 167, 107, 195, 72, 165, 2, 52, 67, 27, 193, 94, 230, 57, 101, 157, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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