Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594e8eb34227853d781da7cf278d366b0740271b8b3008a8bb05cc64ffad5ebe

Tx prefix hash: f56763feb33bac659dc7e36867a64a414876a30de76251e9c2b71031b831f8e8
Tx public key: 8d8020ce4e063dafd2fb9ac768aae1e51eb9a01a56e863d36c9908e700eef80c
Timestamp: 1711549588 Timestamp [UTC]: 2024-03-27 14:26:28 Age [y:d:h:m:s]: 02:050:02:12:21
Block: 987523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547702 RingCT/type: yes/0
Extra: 018d8020ce4e063dafd2fb9ac768aae1e51eb9a01a56e863d36c9908e700eef80c0211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8a0a2a36a41de618b2cab8a64f133976b2d6a6d818687af0cb42a2f5399c4a9e 0.000600000000 1447774 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": 987533, "vin": [ { "gen": { "height": 987523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a0a2a36a41de618b2cab8a64f133976b2d6a6d818687af0cb42a2f5399c4a9e" } } ], "extra": [ 1, 141, 128, 32, 206, 78, 6, 61, 175, 210, 251, 154, 199, 104, 170, 225, 229, 30, 185, 160, 26, 86, 232, 99, 211, 108, 153, 8, 231, 0, 238, 248, 12, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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: