Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aaa32bfacab902ab11a2ebb50599aa2f4cf3264ae00b6046f6ce927b55eaf8f

Tx prefix hash: b01f239b9c26ad474f3ef24653bded62d6b55907ae89548c033e0442d1da99a0
Tx public key: 37e97df24cd615a3cc0201f10864376e26548dc7ff77f844fc3dc1a48d207d59
Timestamp: 1760168700 Timestamp [UCT]: 2025-10-11 07:45:00 Age [y:d:h:m:s]: 00:040:14:16:08
Block: 1387459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29059 RingCT/type: yes/0
Extra: 0137e97df24cd615a3cc0201f10864376e26548dc7ff77f844fc3dc1a48d207d5902110000000917807d39000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c46cf2fa7546b1b406806b26e81e3d21b6e8e7a0acb5bad8d24d30c69a249c98 0.600000000000 1875652 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": 1387469, "vin": [ { "gen": { "height": 1387459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c46cf2fa7546b1b406806b26e81e3d21b6e8e7a0acb5bad8d24d30c69a249c98" } } ], "extra": [ 1, 55, 233, 125, 242, 76, 214, 21, 163, 204, 2, 1, 241, 8, 100, 55, 110, 38, 84, 141, 199, 255, 119, 248, 68, 252, 61, 193, 164, 141, 32, 125, 89, 2, 17, 0, 0, 0, 9, 23, 128, 125, 57, 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