Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53a9069908e3804f5013d152a93eeaf942e731f9a75b1f68c3b5f5ce4b4994f7

Tx prefix hash: 09254e5d32da3a03db4b76400435181aadf337676b99dca8a3d86a3462c117d9
Tx public key: 935281245572c7743e4272335cacc30ed6e5554cc3626d5517009f4b0524e44c
Timestamp: 1704110307 Timestamp [UTC]: 2024-01-01 11:58:27 Age [y:d:h:m:s]: 02:136:18:36:29
Block: 925812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609865 RingCT/type: yes/0
Extra: 01935281245572c7743e4272335cacc30ed6e5554cc3626d5517009f4b0524e44c02110000000752d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b159ff47f8b7f37e55290d889600d8c7a6d2cc33f9fd2b51ebfd785ee6f78165 0.000600000000 1383582 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 dinastycoin-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": 925822, "vin": [ { "gen": { "height": 925812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b159ff47f8b7f37e55290d889600d8c7a6d2cc33f9fd2b51ebfd785ee6f78165" } } ], "extra": [ 1, 147, 82, 129, 36, 85, 114, 199, 116, 62, 66, 114, 51, 92, 172, 195, 14, 214, 229, 85, 76, 195, 98, 109, 85, 23, 0, 159, 75, 5, 36, 228, 76, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: