Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63d429991fd51e7c83ace163cccf88300bbb6e64f1e4ebb0832ef7d65f71c6d1

Tx prefix hash: 8426826afd7e1ccffb10b01e841a2e68d18ab7d666f64629ef56b95abcd8d225
Tx public key: d039c20b523b93b0408c5f4ef502eee80033f60e338872fcf0b18d719fef7419
Timestamp: 1741943651 Timestamp [UTC]: 2025-03-14 09:14:11 Age [y:d:h:m:s]: 01:253:03:56:26
Block: 1239027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444467 RingCT/type: yes/0
Extra: 01d039c20b523b93b0408c5f4ef502eee80033f60e338872fcf0b18d719fef7419021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05774496a2996aae5bcc239049717f2ea8205ad47f305a5e6e18502da529289d 0.000600000000 1725992 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": 1239037, "vin": [ { "gen": { "height": 1239027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05774496a2996aae5bcc239049717f2ea8205ad47f305a5e6e18502da529289d" } } ], "extra": [ 1, 208, 57, 194, 11, 82, 59, 147, 176, 64, 140, 95, 78, 245, 2, 238, 232, 0, 51, 246, 14, 51, 136, 114, 252, 240, 177, 141, 113, 159, 239, 116, 25, 2, 17, 0, 0, 0, 1, 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: