Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb50349bea1fa3348f109f172310f910751ea80d130a9856fc443e305f5a547e

Tx prefix hash: 08fc59a87c4d6198185ab8fbc77df502e3e9ddcd8f6fed55631538b0a875f69e
Tx public key: 83b048e5b49a59646f58db022d0ee2574816bd803b2ac8b580fbcea4c07e1bdb
Timestamp: 1705672739 Timestamp [UCT]: 2024-01-19 13:58:59 Age [y:d:h:m:s]: 01:140:18:32:17
Block: 938737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361772 RingCT/type: yes/0
Extra: 0183b048e5b49a59646f58db022d0ee2574816bd803b2ac8b580fbcea4c07e1bdb02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e9f7c7802137e46026b37d5adc06637a16c15ffbb90a7e1e28570c8c33a7573 0.600000000000 1396815 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": 938747, "vin": [ { "gen": { "height": 938737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e9f7c7802137e46026b37d5adc06637a16c15ffbb90a7e1e28570c8c33a7573" } } ], "extra": [ 1, 131, 176, 72, 229, 180, 154, 89, 100, 111, 88, 219, 2, 45, 14, 226, 87, 72, 22, 189, 128, 59, 42, 200, 181, 128, 251, 206, 164, 192, 126, 27, 219, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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