Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87700340bc94f3b3a479f6070d74ff52035b32ced68eb2e733cc907e9eb58a5

Tx prefix hash: 6bb46055cad23d2881d9062871e7c9d194582dbe3487a425d7159f8a00619c6a
Tx public key: da25cb5af4cf89c52936ad35117a530b2b47f535d952bff522aeb22ab8d85539
Timestamp: 1751241220 Timestamp [UTC]: 2025-06-29 23:53:40 Age [y:d:h:m:s]: 00:316:10:05:14
Block: 1315481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216548 RingCT/type: yes/0
Extra: 01da25cb5af4cf89c52936ad35117a530b2b47f535d952bff522aeb22ab8d8553902110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 638ab0bd172e183b8f8c961087b5694a85d3d81718ed1111cad25833276ea1a0 0.000600000000 1803136 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": 1315491, "vin": [ { "gen": { "height": 1315481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "638ab0bd172e183b8f8c961087b5694a85d3d81718ed1111cad25833276ea1a0" } } ], "extra": [ 1, 218, 37, 203, 90, 244, 207, 137, 197, 41, 54, 173, 53, 17, 122, 83, 11, 43, 71, 245, 53, 217, 82, 191, 245, 34, 174, 178, 42, 184, 216, 85, 57, 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: