Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2547755f937f5d3bd111939573188f912e47f766b3e70808b87a73473a5736

Tx prefix hash: dc585af8b1e0c68d0292c700223641384d9078c20e867c7a7296de30a56925c4
Tx public key: 22c93898e5817528dd752674c830cff6d29169c3e371e25071d6b79e7000313b
Timestamp: 1757207564 Timestamp [UTC]: 2025-09-07 01:12:44 Age [y:d:h:m:s]: 01:073:15:57:50
Block: 1363010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319023 RingCT/type: yes/0
Extra: 0122c93898e5817528dd752674c830cff6d29169c3e371e25071d6b79e7000313b021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b5ae625db96fea5fa9e721cbf436d4534d9df5a9c3a2d33940453e8d6e1dd72a 0.000600000000 1851049 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": 1363020, "vin": [ { "gen": { "height": 1363010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5ae625db96fea5fa9e721cbf436d4534d9df5a9c3a2d33940453e8d6e1dd72a" } } ], "extra": [ 1, 34, 201, 56, 152, 229, 129, 117, 40, 221, 117, 38, 116, 200, 48, 207, 246, 210, 145, 105, 195, 227, 113, 226, 80, 113, 214, 183, 158, 112, 0, 49, 59, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: