Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84992816b69d6ed9e0c7a751330b6c619a260c3f823ef194a6519abd1b1759b1

Tx prefix hash: 2e44a58d77c00de6e5301c48295a1192d3fe942ca2596996d8ef44c03038e536
Tx public key: 2f984dd2ecaf3e72e7620c91a0ba6111ecc852b3fb6133ac6823f095de265d22
Timestamp: 1761703886 Timestamp [UCT]: 2025-10-29 02:11:26 Age [y:d:h:m:s]: 00:011:16:45:16
Block: 1400194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8361 RingCT/type: yes/0
Extra: 012f984dd2ecaf3e72e7620c91a0ba6111ecc852b3fb6133ac6823f095de265d2202110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bddbe3c425e176359cb2ff5ad226fe99e191172f2a67f3e18398341591fb879 0.600000000000 1888501 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": 1400204, "vin": [ { "gen": { "height": 1400194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bddbe3c425e176359cb2ff5ad226fe99e191172f2a67f3e18398341591fb879" } } ], "extra": [ 1, 47, 152, 77, 210, 236, 175, 62, 114, 231, 98, 12, 145, 160, 186, 97, 17, 236, 200, 82, 179, 251, 97, 51, 172, 104, 35, 240, 149, 222, 38, 93, 34, 2, 17, 0, 0, 0, 3, 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