Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43863aaa9b2ee9e43479462f115213d6063b4f4bb00d00701c879cb1fe067b7

Tx prefix hash: 87bfa3253c096a2d5b9f2f788c82ab9d855847eedcbfad17c838c7946a2b7028
Tx public key: 2aeb46c550ad537ff64aa47b4e9a1528f75ffa9ff6ebd2e5f13cbb2db8f2f106
Timestamp: 1749327366 Timestamp [UCT]: 2025-06-07 20:16:06 Age [y:d:h:m:s]: 00:155:17:48:24
Block: 1300144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108982 RingCT/type: yes/0
Extra: 012aeb46c550ad537ff64aa47b4e9a1528f75ffa9ff6ebd2e5f13cbb2db8f2f10602110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7039a91ca5a972cac3aea9caa3653ecbf042a1547eadae700d4abd5643866bd 0.600000000000 1787691 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": 1300154, "vin": [ { "gen": { "height": 1300144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7039a91ca5a972cac3aea9caa3653ecbf042a1547eadae700d4abd5643866bd" } } ], "extra": [ 1, 42, 235, 70, 197, 80, 173, 83, 127, 246, 74, 164, 123, 78, 154, 21, 40, 247, 95, 250, 159, 246, 235, 210, 229, 241, 60, 187, 45, 184, 242, 241, 6, 2, 17, 0, 0, 0, 5, 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