Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 698e704e02d679a888d6dc356622a83d79dde3d43458d3b59abbc77c8f05fa79

Tx prefix hash: 934dd074f43cc241856b4393ea2d207df8ae3d25c216ebbb35f2b66a32fca085
Tx public key: 484098c00544d0105e428be86a7a15113de21ad66912fcbdedbcc28b1f0e65f4
Timestamp: 1720450796 Timestamp [UTC]: 2024-07-08 14:59:56 Age [y:d:h:m:s]: 01:315:08:52:47
Block: 1061297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477296 RingCT/type: yes/0
Extra: 01484098c00544d0105e428be86a7a15113de21ad66912fcbdedbcc28b1f0e65f402110000000491e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 042b0917dc285602fea7a0fbb60d5ff9d85d3375f51114af8d402f2799d3314b 0.000600000000 1531788 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": 1061307, "vin": [ { "gen": { "height": 1061297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "042b0917dc285602fea7a0fbb60d5ff9d85d3375f51114af8d402f2799d3314b" } } ], "extra": [ 1, 72, 64, 152, 192, 5, 68, 208, 16, 94, 66, 139, 232, 106, 122, 21, 17, 61, 226, 26, 214, 105, 18, 252, 189, 237, 188, 194, 139, 31, 14, 101, 244, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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: