Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d87d03026b2817f8923d246a0e4e7b2a25b31d5077fac1c34beab4bd0ff8396

Tx prefix hash: 87ec82161535840fe4bcf0085bf92c6b8bd5df281a44a318a15488e0682bdbce
Tx public key: 12e585957261637d40e269f5381915085f169687e9b54b4cba5f0b3e6c24d760
Timestamp: 1723851845 Timestamp [UTC]: 2024-08-16 23:44:05 Age [y:d:h:m:s]: 01:270:08:29:16
Block: 1089492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443974 RingCT/type: yes/0
Extra: 0112e585957261637d40e269f5381915085f169687e9b54b4cba5f0b3e6c24d760021100000004e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 116aae591367e898c3f964ec6d1e98e405bfef0228d686a119320b5280bdfab0 0.000600000000 1564113 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": 1089502, "vin": [ { "gen": { "height": 1089492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "116aae591367e898c3f964ec6d1e98e405bfef0228d686a119320b5280bdfab0" } } ], "extra": [ 1, 18, 229, 133, 149, 114, 97, 99, 125, 64, 226, 105, 245, 56, 25, 21, 8, 95, 22, 150, 135, 233, 181, 75, 76, 186, 95, 11, 62, 108, 36, 215, 96, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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: