Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cea4ac5615561078ff3fd04a28f61500a5e8f05caf730106db414de3184c89c9

Tx prefix hash: b90408cfedf9992586b44eb37ba4a88c3196debb94282425a8d76b7de6995c8d
Tx public key: 10873e100ad8e0f7e87ea8e515bd1a336b753ef3d3854b5406a4e9fec07b7fc7
Timestamp: 1717314493 Timestamp [UCT]: 2024-06-02 07:48:13 Age [y:d:h:m:s]: 00:325:23:00:14
Block: 1035303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232960 RingCT/type: yes/0
Extra: 0110873e100ad8e0f7e87ea8e515bd1a336b753ef3d3854b5406a4e9fec07b7fc702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7c6ddb03345f7aaeccffaf8116ee7d9a63bb8504812d83e51553ac8f150cbed 0.600000000000 1503824 of 15

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": 1035313, "vin": [ { "gen": { "height": 1035303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c6ddb03345f7aaeccffaf8116ee7d9a63bb8504812d83e51553ac8f150cbed" } } ], "extra": [ 1, 16, 135, 62, 16, 10, 216, 224, 247, 232, 126, 168, 229, 21, 189, 26, 51, 107, 117, 62, 243, 211, 133, 75, 84, 6, 164, 233, 254, 192, 123, 127, 199, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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