Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 696d5ced43ea97576287b1ca5092e2f70239a70fef5cfd7546bef216ef7dcd9c

Tx prefix hash: 2ec7aafdcd70f8c4841e0e4ca01c31db798fcc60e946fea5112fc23cee42cb82
Tx public key: 47fb0f17165adb4c58d35499237bc7dc77e275e6c7d7ce0c0b377e86269c485a
Timestamp: 1700708903 Timestamp [UCT]: 2023-11-23 03:08:23 Age [y:d:h:m:s]: 01:093:05:01:32
Block: 897618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327744 RingCT/type: yes/0
Extra: 0147fb0f17165adb4c58d35499237bc7dc77e275e6c7d7ce0c0b377e86269c485a02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.651356774000 dcy

stealth address amount amount idx
00: f3ddbe6c43d91dbf8e3a67bac01cba74a423528d55ebb88f5cd2a22a4b367b88 0.651356774000 1353999 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": 897628, "vin": [ { "gen": { "height": 897618 } } ], "vout": [ { "amount": 651356774, "target": { "key": "f3ddbe6c43d91dbf8e3a67bac01cba74a423528d55ebb88f5cd2a22a4b367b88" } } ], "extra": [ 1, 71, 251, 15, 23, 22, 90, 219, 76, 88, 211, 84, 153, 35, 123, 199, 220, 119, 226, 117, 230, 199, 215, 206, 12, 11, 55, 126, 134, 38, 156, 72, 90, 2, 17, 0, 0, 0, 5, 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