Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c893a9f58e13dd467fef89fadab8a97280275befd19c3b0dbd5fcc3fce5897

Tx prefix hash: 7f6eec464b999ed7fa9ce202a1b7e38a0cdb2db2ee8e7c8fd384f763f1a86b9a
Tx public key: 726b5df3e78a9bfcc24b6562eece720fabfcc9754bcdaf021086301f9faf3a5e
Timestamp: 1741667091 Timestamp [UTC]: 2025-03-11 04:24:51 Age [y:d:h:m:s]: 01:251:10:49:32
Block: 1236731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443728 RingCT/type: yes/0
Extra: 01726b5df3e78a9bfcc24b6562eece720fabfcc9754bcdaf021086301f9faf3a5e021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f5792a7f952c2b90c9d8e2facfdca9fa7ee0a0166d75bffad3625a1bed4d512c 0.000600000000 1723682 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": 1236741, "vin": [ { "gen": { "height": 1236731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5792a7f952c2b90c9d8e2facfdca9fa7ee0a0166d75bffad3625a1bed4d512c" } } ], "extra": [ 1, 114, 107, 93, 243, 231, 138, 155, 252, 194, 75, 101, 98, 238, 206, 114, 15, 171, 252, 201, 117, 75, 205, 175, 2, 16, 134, 48, 31, 159, 175, 58, 94, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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: