Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c571edd3d361d6e7ea0c8db3c7d74e114a00f36c08e187ce1c2f72d6134e71

Tx prefix hash: 29f27a40aaea63ee0054384ada663d003e32d4795e64a18ca06ba727ddbe2e77
Tx public key: 2aaa7ae80533fa726b7835c5558d3a307164212af5bf542b096ef88d30775342
Timestamp: 1761637912 Timestamp [UTC]: 2025-10-28 07:51:52 Age [y:d:h:m:s]: 01:020:05:06:59
Block: 1399649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280741 RingCT/type: yes/0
Extra: 012aaa7ae80533fa726b7835c5558d3a307164212af5bf542b096ef88d3077534202110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d2a1ac282d6db6b1867abbbc9e34098e062b9ea283a4d009f2733d848a238c9 0.000600000000 1887954 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": 1399659, "vin": [ { "gen": { "height": 1399649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2a1ac282d6db6b1867abbbc9e34098e062b9ea283a4d009f2733d848a238c9" } } ], "extra": [ 1, 42, 170, 122, 232, 5, 51, 250, 114, 107, 120, 53, 197, 85, 141, 58, 48, 113, 100, 33, 42, 245, 191, 84, 43, 9, 110, 248, 141, 48, 119, 83, 66, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: