Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ef6c2d3e84a3fad5c1ae1833b7f569831849a55839a90f18591c35b169ae62a

Tx prefix hash: 4a15560558c5c3272c81525b48760c3bc100a0c479216976d87b3bc99a944e81
Tx public key: dfb303a220ff3c583ae6045c8aa1fae1343f01a41a2a1105d022a4201e81ec61
Timestamp: 1581951371 Timestamp [UCT]: 2020-02-17 14:56:11 Age [y:d:h:m:s]: 04:277:07:18:43
Block: 66948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090458 RingCT/type: yes/0
Extra: 01dfb303a220ff3c583ae6045c8aa1fae1343f01a41a2a1105d022a4201e81ec610211000000020aca7173000000000000000000

1 output(s) for total of 368.299322213000 dcy

stealth address amount amount idx
00: 91af4f9c770824a37a6d1d5e26725e4bc4e5f805349de0c9394929a77a880c47 368.299322213000 123211 of 0

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": 66958, "vin": [ { "gen": { "height": 66948 } } ], "vout": [ { "amount": 368299322213, "target": { "key": "91af4f9c770824a37a6d1d5e26725e4bc4e5f805349de0c9394929a77a880c47" } } ], "extra": [ 1, 223, 179, 3, 162, 32, 255, 60, 88, 58, 230, 4, 92, 138, 161, 250, 225, 52, 63, 1, 164, 26, 42, 17, 5, 208, 34, 164, 32, 30, 129, 236, 97, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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