Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d148929666589d96d68a8562874c854aace680e0b5115f6288a86dcc82e9b9ea

Tx prefix hash: 2f228b9d29446fbf19681311715db3bdabcffc16a339868a40ada2712f3ae1b3
Tx public key: c94b7fa7c35f38dafb3c074d7248ea13e2ca824fd7906532295f24867255ebb6
Timestamp: 1719456763 Timestamp [UTC]: 2024-06-27 02:52:43 Age [y:d:h:m:s]: 01:326:12:04:16
Block: 1053048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485275 RingCT/type: yes/0
Extra: 01c94b7fa7c35f38dafb3c074d7248ea13e2ca824fd7906532295f24867255ebb602110000000959dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c35cab094df0bb638cb2b64d268b9c10a098abe2545ed717fe005bc1f59e44f 0.000600000000 1523393 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": 1053058, "vin": [ { "gen": { "height": 1053048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c35cab094df0bb638cb2b64d268b9c10a098abe2545ed717fe005bc1f59e44f" } } ], "extra": [ 1, 201, 75, 127, 167, 195, 95, 56, 218, 251, 60, 7, 77, 114, 72, 234, 19, 226, 202, 130, 79, 215, 144, 101, 50, 41, 95, 36, 134, 114, 85, 235, 182, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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: