Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e34a16cdb4da2c3fdcec5d13fd7c6c09f4e5793f95219e7ac3239788e5e40509

Tx prefix hash: 59eddad04c3af0a5b2ed47095662d69878bad0108b7648ee1c35a6de8ee3ccd6
Tx public key: 6eb0eab5fdb94b5a09a0b0ae7e28b39b3f7d5f8df11101b992bdfcc98f1f58d7
Timestamp: 1794228845 Timestamp [UTC]: 2026-11-09 12:54:05 Age [y:d:h:m:s]: 00:009:20:08:17
Block: 1674239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 7533 RingCT/type: yes/0
Extra: 016eb0eab5fdb94b5a09a0b0ae7e28b39b3f7d5f8df11101b992bdfcc98f1f58d7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b8d3d419e676950ea4d47877317228d9ac50efe939cca62b4035dd034f28d502 0.000600000000 2165001 of 15 <6e>

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": 1674249, "vin": [ { "gen": { "height": 1674239 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "b8d3d419e676950ea4d47877317228d9ac50efe939cca62b4035dd034f28d502", "view_tag": "6e" } } } ], "extra": [ 1, 110, 176, 234, 181, 253, 185, 75, 90, 9, 160, 176, 174, 126, 40, 179, 155, 63, 125, 95, 141, 241, 17, 1, 185, 146, 189, 252, 201, 143, 31, 88, 215 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: