Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de8794f0143fa7dedc3ec71ac80e7c64036b0db0841068a35daa70ca94fcee13

Tx prefix hash: 1bb72ddae7ef05e32fb716d3627b275bfb7eb53ce51976a554a1b100fe129f63
Tx public key: 2ca996086859dae856ea3d945259cc1105b5c4031b44b026fdad85d2e7ec5c05
Timestamp: 1768813246 Timestamp [UTC]: 2026-01-19 09:00:46 Age [y:d:h:m:s]: 00:303:15:39:20
Block: 1458962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222546 RingCT/type: yes/0
Extra: 012ca996086859dae856ea3d945259cc1105b5c4031b44b026fdad85d2e7ec5c05021100000003215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 446a7fc3491fc045e7bcf2c9b0ae01321e6314492dc18dc2d1b230bcb868e761 0.000600000000 1948112 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": 1458972, "vin": [ { "gen": { "height": 1458962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "446a7fc3491fc045e7bcf2c9b0ae01321e6314492dc18dc2d1b230bcb868e761" } } ], "extra": [ 1, 44, 169, 150, 8, 104, 89, 218, 232, 86, 234, 61, 148, 82, 89, 204, 17, 5, 181, 196, 3, 27, 68, 176, 38, 253, 173, 133, 210, 231, 236, 92, 5, 2, 17, 0, 0, 0, 3, 33, 91, 191, 137, 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: