Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426bfd66b214ba3ccd717b6626845c2e5e383e88986dffc00a5611ad26b81a80

Tx prefix hash: 4265e3e8bb85b16793fbfa6c3e2180e70c0c8d24326ce4a19f74918567a3b4bd
Tx public key: 634f7ba3b39183067fa346cb7ffd7dd498c1704aafaa5d0c3ed95f3dd343838f
Timestamp: 1768363397 Timestamp [UTC]: 2026-01-14 04:03:17 Age [y:d:h:m:s]: 00:307:14:23:22
Block: 1455221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225337 RingCT/type: yes/0
Extra: 01634f7ba3b39183067fa346cb7ffd7dd498c1704aafaa5d0c3ed95f3dd343838f021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 637fbf363aa35dce98e4d25a5f3620c9c88587f56aeaa20622421c4d01b86568 0.000600000000 1944315 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": 1455231, "vin": [ { "gen": { "height": 1455221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "637fbf363aa35dce98e4d25a5f3620c9c88587f56aeaa20622421c4d01b86568" } } ], "extra": [ 1, 99, 79, 123, 163, 179, 145, 131, 6, 127, 163, 70, 203, 127, 253, 125, 212, 152, 193, 112, 74, 175, 170, 93, 12, 62, 217, 95, 61, 211, 67, 131, 143, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: