Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3deee0778fe2b0cda8452647237efec339642d6492f547495bf92aa284e12d0

Tx prefix hash: 3cb5b2a8abda8240168076f63e4393e782ce024d5fc9a92ada334213d3896e18
Tx public key: ebf9f2d214b0f8304bdfe1b49c7818e8e7c7dd6d59e933c9b99490a6c5014b23
Timestamp: 1698466863 Timestamp [UCT]: 2023-10-28 04:21:03 Age [y:d:h:m:s]: 01:120:05:01:00
Block: 879253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346868 RingCT/type: yes/0
Extra: 01ebf9f2d214b0f8304bdfe1b49c7818e8e7c7dd6d59e933c9b99490a6c5014b23021100000011e6d27f9c000000000000000000

1 output(s) for total of 0.749324322000 dcy

stealth address amount amount idx
00: 616624a69ed3dbc9cc33f90d0f8b468d0bb29bdca8b45c49c76c73a47622055a 0.749324322000 1334759 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": 879263, "vin": [ { "gen": { "height": 879253 } } ], "vout": [ { "amount": 749324322, "target": { "key": "616624a69ed3dbc9cc33f90d0f8b468d0bb29bdca8b45c49c76c73a47622055a" } } ], "extra": [ 1, 235, 249, 242, 210, 20, 176, 248, 48, 75, 223, 225, 180, 156, 120, 24, 232, 231, 199, 221, 109, 89, 233, 51, 201, 185, 148, 144, 166, 197, 1, 75, 35, 2, 17, 0, 0, 0, 17, 230, 210, 127, 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