Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1fb53d3d4c9725cd3b3b6cebd13c6640d67cb4da666e08f573eb83e39b5385

Tx prefix hash: 2f60e334c2e78a10cf7fb41b8282e04403a00c5faf214d9f5cee507ee2a8b484
Tx public key: d580fd92e8942de9a72c60104927983ee21605f190de8cedd9694473e2fa5f84
Timestamp: 1669665613 Timestamp [UCT]: 2022-11-28 20:00:13 Age [y:d:h:m:s]: 03:005:05:55:55
Block: 641157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 784084 RingCT/type: yes/0
Extra: 01d580fd92e8942de9a72c60104927983ee21605f190de8cedd9694473e2fa5f8402110000000475e3f0e9000000000000000000

1 output(s) for total of 4.608724011000 dcy

stealth address amount amount idx
00: e1dbc466daffe29a320b13d1e9ed106e8aeb34b1237c600b5c47b05809834139 4.608724011000 1080938 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": 641167, "vin": [ { "gen": { "height": 641157 } } ], "vout": [ { "amount": 4608724011, "target": { "key": "e1dbc466daffe29a320b13d1e9ed106e8aeb34b1237c600b5c47b05809834139" } } ], "extra": [ 1, 213, 128, 253, 146, 232, 148, 45, 233, 167, 44, 96, 16, 73, 39, 152, 62, 226, 22, 5, 241, 144, 222, 140, 237, 217, 105, 68, 115, 226, 250, 95, 132, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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