Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b07da69f6e1c636e629742b55fd42aa57fe7223f8a0c12c59d44cac3b5d650f

Tx prefix hash: 98a46e97cc6e72a27a7d03dce93fb2886ef763e45c0272b2a51b780e4ddaa007
Tx public key: de98e6a1956ac5846f2aaab9bc19477f1fe98c15b61fc9ebeb78590714b6e438
Timestamp: 1671546944 Timestamp [UCT]: 2022-12-20 14:35:44 Age [y:d:h:m:s]: 02:110:17:43:37
Block: 656744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600831 RingCT/type: yes/0
Extra: 01de98e6a1956ac5846f2aaab9bc19477f1fe98c15b61fc9ebeb78590714b6e43802110000000483600029000000000000000000

1 output(s) for total of 4.091989185000 dcy

stealth address amount amount idx
00: 35ddb558a4d84fc445ec3ed50f0af9f7950d7e2c629f9fdfdce2c3c02ea6c999 4.091989185000 1097367 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": 656754, "vin": [ { "gen": { "height": 656744 } } ], "vout": [ { "amount": 4091989185, "target": { "key": "35ddb558a4d84fc445ec3ed50f0af9f7950d7e2c629f9fdfdce2c3c02ea6c999" } } ], "extra": [ 1, 222, 152, 230, 161, 149, 106, 197, 132, 111, 42, 170, 185, 188, 25, 71, 127, 31, 233, 140, 21, 182, 31, 201, 235, 235, 120, 89, 7, 20, 182, 228, 56, 2, 17, 0, 0, 0, 4, 131, 96, 0, 41, 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