Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d4b12499ffe1246f3af9758b9db7e351706c9e5cfad21aa20ab1de34038d795

Tx prefix hash: 4f19ab2a1bfcd4bfea914bfc3f3e9c9bbf89addd736b566f37a37ac0a480feeb
Tx public key: 265d5bee2a8fef9591a6f8fdf8bf49910e1282914d9a5619de9fdf42c9085cb6
Timestamp: 1700265329 Timestamp [UCT]: 2023-11-17 23:55:29 Age [y:d:h:m:s]: 01:098:17:13:22
Block: 893937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331698 RingCT/type: yes/0
Extra: 01265d5bee2a8fef9591a6f8fdf8bf49910e1282914d9a5619de9fdf42c9085cb602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.669908704000 dcy

stealth address amount amount idx
00: 7bb17ad2a3fd7e275650698203e1f40a0aabc8fad9132cc0c750dd059f4d3a98 0.669908704000 1350122 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": 893947, "vin": [ { "gen": { "height": 893937 } } ], "vout": [ { "amount": 669908704, "target": { "key": "7bb17ad2a3fd7e275650698203e1f40a0aabc8fad9132cc0c750dd059f4d3a98" } } ], "extra": [ 1, 38, 93, 91, 238, 42, 143, 239, 149, 145, 166, 248, 253, 248, 191, 73, 145, 14, 18, 130, 145, 77, 154, 86, 25, 222, 159, 223, 66, 201, 8, 92, 182, 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