Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 385ffcf8c9c958ccd51cd5749bbf0d126bc6ac986238f2281dfe13f01bfc5f62

Tx prefix hash: b5171ce7c728d1ee884c2169914c8d6c2b050de2037650bbca957fb63f20d421
Tx public key: a0a3b757ad0c43d52f68995078106dd969268621fea6edef05a95b2f80a4fdff
Timestamp: 1699079851 Timestamp [UCT]: 2023-11-04 06:37:31 Age [y:d:h:m:s]: 01:167:02:53:41
Block: 884321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380443 RingCT/type: yes/0
Extra: 01a0a3b757ad0c43d52f68995078106dd969268621fea6edef05a95b2f80a4fdff021100000006faf35c9c000000000000000000

1 output(s) for total of 0.720903998000 dcy

stealth address amount amount idx
00: e7821fb98c74782c0f72a233fea8ec8d5157954b698a219634fd948eb9f8871b 0.720903998000 1340058 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": 884331, "vin": [ { "gen": { "height": 884321 } } ], "vout": [ { "amount": 720903998, "target": { "key": "e7821fb98c74782c0f72a233fea8ec8d5157954b698a219634fd948eb9f8871b" } } ], "extra": [ 1, 160, 163, 183, 87, 173, 12, 67, 213, 47, 104, 153, 80, 120, 16, 109, 217, 105, 38, 134, 33, 254, 166, 237, 239, 5, 169, 91, 47, 128, 164, 253, 255, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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