Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2717d29b83d4a534dc350e8cd3c4339dab0a93fb71d32ac39aa55ec971e7a3

Tx prefix hash: 7ac17240539efc2b794688384a20acce0b52259ffdf175a5bfca6f6c3e48748c
Tx public key: 6c6739d959bd0223830859553342260595b367a1f49d0d052c050d575ed305fc
Timestamp: 1744768745 Timestamp [UTC]: 2025-04-16 01:59:05 Age [y:d:h:m:s]: 00:306:16:59:39
Block: 1262403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216834 RingCT/type: yes/0
Extra: 016c6739d959bd0223830859553342260595b367a1f49d0d052c050d575ed305fc021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f2fedda99c66b2c458d16ee7d3cdb8ef2740286d8fab2d96aec34dec3cea328a 0.000600000000 1749582 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": 1262413, "vin": [ { "gen": { "height": 1262403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2fedda99c66b2c458d16ee7d3cdb8ef2740286d8fab2d96aec34dec3cea328a" } } ], "extra": [ 1, 108, 103, 57, 217, 89, 189, 2, 35, 131, 8, 89, 85, 51, 66, 38, 5, 149, 179, 103, 161, 244, 157, 13, 5, 44, 5, 13, 87, 94, 211, 5, 252, 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) | dinastycoin version: tesla-369