Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e837aeb55838ca905b76c9d44257cc703baffc55d9b0ebced707ba7d5a0b3f

Tx prefix hash: dc1553249f9ed9008fa1fb7d03e0476cf65bb4b8f6131df630672a9d21c91d95
Tx public key: 47a3f032a9a5c52b72a1ab444b36779d587ff6c45d199143e53f97e589cb39b3
Timestamp: 1707600367 Timestamp [UCT]: 2024-02-10 21:26:07 Age [y:d:h:m:s]: 00:250:17:09:54
Block: 954746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179601 RingCT/type: yes/0
Extra: 0147a3f032a9a5c52b72a1ab444b36779d587ff6c45d199143e53f97e589cb39b302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf332e0407f153a36b8e9e5e1e7efa78d3e00745831232a39fc7dd451430f36 0.600000000000 1414028 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": 954756, "vin": [ { "gen": { "height": 954746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf332e0407f153a36b8e9e5e1e7efa78d3e00745831232a39fc7dd451430f36" } } ], "extra": [ 1, 71, 163, 240, 50, 169, 165, 197, 43, 114, 161, 171, 68, 75, 54, 119, 157, 88, 127, 246, 196, 93, 25, 145, 67, 229, 63, 151, 229, 137, 203, 57, 179, 2, 17, 0, 0, 0, 1, 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