Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc1060ff463fb8dd1328e58331c3afd1616922d33203fbd09fbb9c46bba89cd

Tx prefix hash: a2e069354e296db4b54783885426887cc1b66110de1bd098f4fdf913ec5ccd0b
Tx public key: bc2b991f5b414e8b25a41d899939612f22f31c087ec6168130f67631dc638fa0
Timestamp: 1754924512 Timestamp [UTC]: 2025-08-11 15:01:52 Age [y:d:h:m:s]: 01:103:01:19:57
Block: 1344889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338605 RingCT/type: yes/0
Extra: 01bc2b991f5b414e8b25a41d899939612f22f31c087ec6168130f67631dc638fa002110000000fad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 757c5f232e9492f41e258dba4848dce65dcf59aa69a09123e7c59f531dfaed3b 0.000600000000 1832776 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": 1344899, "vin": [ { "gen": { "height": 1344889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "757c5f232e9492f41e258dba4848dce65dcf59aa69a09123e7c59f531dfaed3b" } } ], "extra": [ 1, 188, 43, 153, 31, 91, 65, 78, 139, 37, 164, 29, 137, 153, 57, 97, 47, 34, 243, 28, 8, 126, 198, 22, 129, 48, 246, 118, 49, 220, 99, 143, 160, 2, 17, 0, 0, 0, 15, 173, 121, 72, 208, 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: