Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32bb738ec2f891cfcab623a08ca97dcd98485de9d900a8d301944d0409b04e20

Tx prefix hash: b2ed397b33cf3929af4d08d6c7f38e114b3c6e8b1f3c12030ed9ea345654f1ca
Tx public key: 5ac9e2a37aebf6defd6f450d1857734cbd6532350aae279860ada8b721458e08
Timestamp: 1750778883 Timestamp [UCT]: 2025-06-24 15:28:03 Age [y:d:h:m:s]: 00:149:12:36:50
Block: 1311901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104791 RingCT/type: yes/0
Extra: 015ac9e2a37aebf6defd6f450d1857734cbd6532350aae279860ada8b721458e0802110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01042ef1e0fcca6b2ded1e6d0f49a4f2551df38f5680cbf82210ae0266e4c993 0.600000000000 1799530 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": 1311911, "vin": [ { "gen": { "height": 1311901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01042ef1e0fcca6b2ded1e6d0f49a4f2551df38f5680cbf82210ae0266e4c993" } } ], "extra": [ 1, 90, 201, 226, 163, 122, 235, 246, 222, 253, 111, 69, 13, 24, 87, 115, 76, 189, 101, 50, 53, 10, 174, 39, 152, 96, 173, 168, 183, 33, 69, 142, 8, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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