Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5813cffc461b3b0f79b66777f20a11abe9d15b72e624d9e4e21d3c33eae81c5e

Tx prefix hash: 08f7c4d53440245ffde94563d6f7e44c7fe496652b5e467fc259cd6893b43286
Tx public key: 069ea3b2e3a7e82ec8c5d447ceab942a63b20a537bbb1289bd662574217883ce
Timestamp: 1755727172 Timestamp [UTC]: 2025-08-20 21:59:32 Age [y:d:h:m:s]: 00:272:03:43:31
Block: 1350861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187792 RingCT/type: yes/0
Extra: 01069ea3b2e3a7e82ec8c5d447ceab942a63b20a537bbb1289bd662574217883ce02110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 646e68a42cfecc093b829e1354fc3c40dcde559302f8fdcefb3da6e0bc80343e 0.000600000000 1838808 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": 1350871, "vin": [ { "gen": { "height": 1350861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "646e68a42cfecc093b829e1354fc3c40dcde559302f8fdcefb3da6e0bc80343e" } } ], "extra": [ 1, 6, 158, 163, 178, 227, 167, 232, 46, 200, 197, 212, 71, 206, 171, 148, 42, 99, 178, 10, 83, 123, 187, 18, 137, 189, 102, 37, 116, 33, 120, 131, 206, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: