Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67fd20f1dea95c8d6c405962d0519e934cfcd1457527b8500ffa3478f9e860fb

Tx prefix hash: e61d7ca393da59170e8dfb447112e101397ed2a64adbeb7492fd385e943e15b8
Tx public key: 592fc74595d8bf3300b046bfd2ed8ebd913dd949191d7587fddd0103a0200247
Timestamp: 1743151081 Timestamp [UTC]: 2025-03-28 08:38:01 Age [y:d:h:m:s]: 01:238:02:53:40
Block: 1248997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434384 RingCT/type: yes/0
Extra: 01592fc74595d8bf3300b046bfd2ed8ebd913dd949191d7587fddd0103a0200247021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 63960f7a7856e555fe4998d9d91a8749a2b8b58802b47943894e0cfd6c4d9d35 0.000600000000 1736032 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": 1249007, "vin": [ { "gen": { "height": 1248997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63960f7a7856e555fe4998d9d91a8749a2b8b58802b47943894e0cfd6c4d9d35" } } ], "extra": [ 1, 89, 47, 199, 69, 149, 216, 191, 51, 0, 176, 70, 191, 210, 237, 142, 189, 145, 61, 217, 73, 25, 29, 117, 135, 253, 221, 1, 3, 160, 32, 2, 71, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: