Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7b211e11a5464db30b236a5a322d16959971e2a3517b5227dca1ceab282ea8

Tx prefix hash: 3aeb42df3608ba6dc4de8c38b610f9f26b7ed38f9cb5219ab077d2442a8a2594
Tx public key: 033f09d8204adf10e20f52037fd78ed022b24c4a4f4fddcd73e781100009893a
Timestamp: 1769840440 Timestamp [UTC]: 2026-01-31 06:20:40 Age [y:d:h:m:s]: 00:014:22:19:31
Block: 1467421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10677 RingCT/type: yes/0
Extra: 01033f09d8204adf10e20f52037fd78ed022b24c4a4f4fddcd73e781100009893a02110000000149d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 00a5c4064883aaefc897cdca1da087dd45f0c5b8caf8132ef397ca7f8185a42c 0.000600000000 1956661 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": 1467431, "vin": [ { "gen": { "height": 1467421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a5c4064883aaefc897cdca1da087dd45f0c5b8caf8132ef397ca7f8185a42c" } } ], "extra": [ 1, 3, 63, 9, 216, 32, 74, 223, 16, 226, 15, 82, 3, 127, 215, 142, 208, 34, 178, 76, 74, 79, 79, 221, 205, 115, 231, 129, 16, 0, 9, 137, 58, 2, 17, 0, 0, 0, 1, 73, 215, 62, 152, 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) | dinastycoin version: tesla-369