Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6725281b564cbc64e6984fbe517f1f47b8aab6a9626b4fc57c6efbbe1120d8f

Tx prefix hash: 88bc0bcd94f34c83c5a048ebe8a71d3ad48a70e25d3fbfc231cd96b21e0f9b7e
Tx public key: e511c2f4aa661beb6b15dcc1686923b208a692f64e2a871ac6186e2b9b77c244
Timestamp: 1710213393 Timestamp [UCT]: 2024-03-12 03:16:33 Age [y:d:h:m:s]: 01:007:08:23:34
Block: 976430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266246 RingCT/type: yes/0
Extra: 01e511c2f4aa661beb6b15dcc1686923b208a692f64e2a871ac6186e2b9b77c2440211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb108210d241e6ea92fb2b1e17cdf732f7f2ac7d097947af4e9a4732e64c4bb3 0.600000000000 1436425 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 dinasty-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": 976440, "vin": [ { "gen": { "height": 976430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb108210d241e6ea92fb2b1e17cdf732f7f2ac7d097947af4e9a4732e64c4bb3" } } ], "extra": [ 1, 229, 17, 194, 244, 170, 102, 27, 235, 107, 21, 220, 193, 104, 105, 35, 178, 8, 166, 146, 246, 78, 42, 135, 26, 198, 24, 110, 43, 155, 119, 194, 68, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8