Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73db2dc1c2417b3b63379a62e6f8bd9876fd8d1682f8df632b457c578cfb0c0e

Tx prefix hash: ffb862e5a4211a816889d5dc652e7b4810f4e81f0d0afa09872026a2d2dec71d
Tx public key: d0e623bd7f0c10b5663e85ab88a7d74f9f770f598fb5a0637358ed7ebe72b216
Timestamp: 1757017698 Timestamp [UCT]: 2025-09-04 20:28:18 Age [y:d:h:m:s]: 00:124:04:14:16
Block: 1361412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88845 RingCT/type: yes/0
Extra: 01d0e623bd7f0c10b5663e85ab88a7d74f9f770f598fb5a0637358ed7ebe72b216021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b59a0e170df93cf6a0cfb200e2a110cec4062acc035e72a435e6f4bca98eecec 0.600000000000 1849427 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": 1361422, "vin": [ { "gen": { "height": 1361412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b59a0e170df93cf6a0cfb200e2a110cec4062acc035e72a435e6f4bca98eecec" } } ], "extra": [ 1, 208, 230, 35, 189, 127, 12, 16, 181, 102, 62, 133, 171, 136, 167, 215, 79, 159, 119, 15, 89, 143, 181, 160, 99, 115, 88, 237, 126, 190, 114, 178, 22, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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