Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d1e2cfd642e01aa5036c33cadb2d4bbc82eb6089ec2d8eea0bd093df8cca78

Tx prefix hash: 286784932fb4c037bdacae5ef13f7331cbd33bd13484334254bb9012bf8d9410
Tx public key: 6ac9fca87882f140028c1ea9d308b31e5c056836c086e86c5634c2c4f82bc70a
Timestamp: 1771731861 Timestamp [UTC]: 2026-02-22 03:44:21 Age [y:d:h:m:s]: 00:270:01:44:28
Block: 1483083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198584 RingCT/type: yes/0
Extra: 016ac9fca87882f140028c1ea9d308b31e5c056836c086e86c5634c2c4f82bc70a021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: edd532288731a4fb4a278c501ba3ddb252b4da1b1d41d5559d5fdba5069797a0 0.000600000000 1972487 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": 1483093, "vin": [ { "gen": { "height": 1483083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd532288731a4fb4a278c501ba3ddb252b4da1b1d41d5559d5fdba5069797a0" } } ], "extra": [ 1, 106, 201, 252, 168, 120, 130, 241, 64, 2, 140, 30, 169, 211, 8, 179, 30, 92, 5, 104, 54, 192, 134, 232, 108, 86, 52, 194, 196, 248, 43, 199, 10, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: