Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b401f4bc1b9d42591d68a0b71b22fd5b3c1443ecc93edaad850a70e38c69fdfe

Tx prefix hash: 11d2a00a2f95a8dcf0de4a251833c9ce5e4eb5cd2b47b06918b6d16a819b9dc0
Tx public key: 78f7d50f19ed959137d1f91a2819419970e077f1ce90e47eef096b6b27dd0c46
Timestamp: 1712555278 Timestamp [UTC]: 2024-04-08 05:47:58 Age [y:d:h:m:s]: 02:228:07:45:22
Block: 995805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687689 RingCT/type: yes/0
Extra: 0178f7d50f19ed959137d1f91a2819419970e077f1ce90e47eef096b6b27dd0c4602110000000a0011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8b752d41cba16a73fc92be7a21213e9979c04d143016a1ddccf24b0a3189ca79 0.000600000000 1456219 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": 995815, "vin": [ { "gen": { "height": 995805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b752d41cba16a73fc92be7a21213e9979c04d143016a1ddccf24b0a3189ca79" } } ], "extra": [ 1, 120, 247, 213, 15, 25, 237, 149, 145, 55, 209, 249, 26, 40, 25, 65, 153, 112, 224, 119, 241, 206, 144, 228, 126, 239, 9, 107, 107, 39, 221, 12, 70, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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: