Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80fce00938e6fa19910a0ce575484a250f48879b10e2bf111b24d55e0a493fbf

Tx prefix hash: 605c0c61684bf639d44e41a1272bdd00ec823f09be7ad6da4f6f9fbcf046a0e3
Tx public key: d19b2032fcb8dd5fdf5de28263ed94390df8d505aa22afc5a652cad727305fe9
Timestamp: 1774613615 Timestamp [UTC]: 2026-03-27 12:13:35 Age [y:d:h:m:s]: 00:235:12:15:05
Block: 1506918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173835 RingCT/type: yes/0
Extra: 01d19b2032fcb8dd5fdf5de28263ed94390df8d505aa22afc5a652cad727305fe9021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2ba0dcbf443e3f5d4833875af17aac9bd3aa8dd524434fc53d1b5e8b0a7b7c6 0.000600000000 1996668 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": 1506928, "vin": [ { "gen": { "height": 1506918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2ba0dcbf443e3f5d4833875af17aac9bd3aa8dd524434fc53d1b5e8b0a7b7c6" } } ], "extra": [ 1, 209, 155, 32, 50, 252, 184, 221, 95, 223, 93, 226, 130, 99, 237, 148, 57, 13, 248, 213, 5, 170, 34, 175, 197, 166, 82, 202, 215, 39, 48, 95, 233, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: