Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e6082db9801fa17b73c33441d3b8f2a9b7752a9c4ca815593f9a8bc76a67bf

Tx prefix hash: e84840b96db383eb39a91cc8dab5d70375c195ccc26dbf022a90f48b11d1ef2d
Tx public key: 40a8418b416937a116db5b179065785d422370dc5e4666bcf58a81a7f17f36cf
Timestamp: 1760837147 Timestamp [UTC]: 2025-10-19 01:25:47 Age [y:d:h:m:s]: 01:027:06:27:35
Block: 1393007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285743 RingCT/type: yes/0
Extra: 0140a8418b416937a116db5b179065785d422370dc5e4666bcf58a81a7f17f36cf02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ed96ac815566f2d4b7ac91a74e1a79757c6e628d55e688d46248b0e687bd80b 0.000600000000 1881264 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": 1393017, "vin": [ { "gen": { "height": 1393007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ed96ac815566f2d4b7ac91a74e1a79757c6e628d55e688d46248b0e687bd80b" } } ], "extra": [ 1, 64, 168, 65, 139, 65, 105, 55, 161, 22, 219, 91, 23, 144, 101, 120, 93, 66, 35, 112, 220, 94, 70, 102, 188, 245, 138, 129, 167, 241, 127, 54, 207, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: