Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0793afce430f6081aa5e7934c1a3036aef98fc6ff42e972b5005e87e95a014f

Tx prefix hash: 31de1bed7e68753631df8964105821b547c889f83cfdd513faf2cd0a020ef045
Tx public key: ac78c7b4d8d73f1145d3c5462907dabc7675b3e808b7e5e225a4ec6a583597df
Timestamp: 1707949150 Timestamp [UCT]: 2024-02-14 22:19:10 Age [y:d:h:m:s]: 01:051:18:54:53
Block: 957639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298045 RingCT/type: yes/0
Extra: 01ac78c7b4d8d73f1145d3c5462907dabc7675b3e808b7e5e225a4ec6a583597df0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a2e3954549132ad5e13e3a0ddb4ad837d0af3e267b48d52b32d66809b6c16aa 0.600000000000 1416959 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": 957649, "vin": [ { "gen": { "height": 957639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a2e3954549132ad5e13e3a0ddb4ad837d0af3e267b48d52b32d66809b6c16aa" } } ], "extra": [ 1, 172, 120, 199, 180, 216, 215, 63, 17, 69, 211, 197, 70, 41, 7, 218, 188, 118, 117, 179, 232, 8, 183, 229, 226, 37, 164, 236, 106, 88, 53, 151, 223, 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): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8