Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d51b98b9982e3733488ad38c85c8ac921626f4103dbf02b32d3c7b37cb32f77

Tx prefix hash: 5aa90e3bd94666a9f240d4798e5ed0dcc99079f498cd74dee5dbeb6901e4ccea
Tx public key: 8b66d55811e073cc4fb288b456cd9862c5f3365e22a95485c895625a39f5c90a
Timestamp: 1708426880 Timestamp [UCT]: 2024-02-20 11:01:20 Age [y:d:h:m:s]: 01:095:05:30:24
Block: 961613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329130 RingCT/type: yes/0
Extra: 018b66d55811e073cc4fb288b456cd9862c5f3365e22a95485c895625a39f5c90a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4ef9dc934b07e19aa710c941b5e8dfa5e8dfdaa1ccc755ff9b791cc28bd7381 0.600000000000 1421224 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": 961623, "vin": [ { "gen": { "height": 961613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4ef9dc934b07e19aa710c941b5e8dfa5e8dfdaa1ccc755ff9b791cc28bd7381" } } ], "extra": [ 1, 139, 102, 213, 88, 17, 224, 115, 204, 79, 178, 136, 180, 86, 205, 152, 98, 197, 243, 54, 94, 34, 169, 84, 133, 200, 149, 98, 90, 57, 245, 201, 10, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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